| 1. | Select the core group that contains the failed server in the core groups window
窗口中，选择包含故障服务器的核心组。 |
| 2. | Locate the static policy that is associated with the failed server and select the
定位与故障服务器相关联的静态策略，并选择 |
| 3. | This causes a recovery process for the failed server to begin on the peer server
然后，在对等服务器上开始进行故障服务器的恢复处理。 |
| 4. | Now , the only server that is listed in static group servers is the failed server
现在，在static group servers中列出的这台服务器即为故障服务器。 |
| 5. | And supports the resolution of in - doubt transactions without the need to wait for the failed server to restart
，它将完成尚未处理的事务，而不用等待重启出现故障的服务器。 |
| 6. | After peer recovery processing is complete , you must remove this additional entry before the failed server is restarted
在对等恢复处理结束后，必须删除添加的条目然后重启服务器。 |
| 7. | When recovery processing is complete and before the failed server is restarted , the configuration changes that you made must be reversed
当恢复处理完成且在故障服务器重启之前，需要重新修改配置。 |
| 8. | Prior to websphere application server v6 , it was necessary to restart a failed server to perform recovery processing
在websphere application server v6之前，要执行恢复处理，必须重启出现故障的服务器。 |
| 9. | This happen because the command may try the fail server first and then wait to time out before trying the alternate server
发生这种情况是因为命令首先会尝试出故障的服务器然后等超时后才试著使用其它可替代的服务器。 |
| 10. | Version 6 . 0 introduces the ability for a peer server another cluster member to process the recovery logs of a failed server while the peer continues to manage its own transactional workload
6 . 0版本引进对等服务器（作为一个集群成员） ，使其在管理自身事务工作的同时，能处理故障服务器的恢复日志。 |
